patch: DecodeEntity doesn't honor contentType #142
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The issue lie's in this section:
wrp-go/wrphttp/decoders.go
Lines 45 to 57 in e3db47f
Where it sets
entity.Bytes
to a set of json bytes instead of honoring the content-typeformat
This eventually becomes a problem when a user sends a msgpack request to talaria and the device receiving that message then expects a msgpack request body... triggering a decoding error on the device's end
Because candlelight eats the request body when it extracts the wrp message:
wrp-go/wrphttp/decoders.go
Lines 111 to 140 in e3db47f
the solution appears to be to save the request body in the context along with the wrp message. This allows us to keep the api changes to a minimum without introducing larger patch
This patch will require a one liner update to candlelight and scytale.